Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Freeze version of workspace-client library #788

Merged
merged 1 commit into from
Jul 2, 2020

Conversation

vzhukovs
Copy link
Contributor

@vzhukovs vzhukovs commented Jul 2, 2020

What does this PR do?

This changes proposal freezes version for workspace-client from latest to latest tagged 0.0.1-1585913592. To have smooth incoming changes that won't try to break anything after merge eclipse-che/che-workspace-client#31, because eclipse-che/che-workspace-client#31 is going to be merged among with upcoming changes in che-theia.

Signed-off-by: Vladyslav Zhukovskyi vzhukovs@redhat.com

What issues does this PR fix or reference?

Needed for eclipse-che/che#17246

Release Notes

N/A

Docs PR

N/A

@vzhukovs vzhukovs self-assigned this Jul 2, 2020
@vzhukovs vzhukovs changed the title Che#17246 freeze ws client Freeze version of workspace-client library Jul 2, 2020
Signed-off-by: Vladyslav Zhukovskyi <vzhukovs@redhat.com>
@vzhukovs vzhukovs force-pushed the che#17246-freeze-ws-client branch from 6dcf3f3 to 105c8e0 Compare July 2, 2020 11:20
@benoitf
Copy link
Contributor

benoitf commented Jul 2, 2020

it's not already frozen by yarn.lock ?

@vzhukovs
Copy link
Contributor Author

vzhukovs commented Jul 2, 2020

it's not already frozen by yarn.lock ?

In yarn.lock there is frozen latest version. I want to freeze specific version, because when eclipse-che/che-workspace-client#31 will be merged I want to be sure, that everything won't be broken.

And... it's much easier for testing purposes, for testing new library version, it would be better to update version to the latest instead of pushing library to dedicate package and update imports in code.

@azatsarynnyy
Copy link
Member

@benoitf is right. Tag latest already points to 0.0.1-1585913592 in yarn.lock.
So these changes will have no effect unless someone removes yarn.lock.

@vzhukovs
Copy link
Contributor Author

vzhukovs commented Jul 2, 2020

This is temporary solution, which will be reverted with next PR today or afternoon. Because with next PR there will be an update of yarn.lock with fresh dependencies. Or we shouldn't worry, that some PRs will be merged today/afternoon with yarn.lock update? WDYT?

@che-bot
Copy link
Contributor

che-bot commented Jul 2, 2020

✅ E2E Happy path tests succeed 🎉

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:788
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:788

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

@azatsarynnyy
Copy link
Member

This is temporary solution, which will be reverted with next PR today or afternoon. Because with next PR there will be an update of yarn.lock with fresh dependencies. Or we shouldn't worry, that some PRs will be merged today/afternoon with yarn.lock update? WDYT?

I'm ok with that.

@benoitf
Copy link
Contributor

benoitf commented Jul 2, 2020

I'm ok with all solutions, just wanted to emphasis that for now we're stuck to a given version even with 'latest'

@vzhukovs
Copy link
Contributor Author

vzhukovs commented Jul 2, 2020

Yep, it will be reverted soon

@vzhukovs vzhukovs merged commit 74a9a3a into master Jul 2, 2020
@vzhukovs vzhukovs deleted the che#17246-freeze-ws-client branch July 2, 2020 12:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants